Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1440

reference
123-tree-1
name
1440
tree-preservation-order

undefined

123-tpo-1
uprn
address-text
point
POINT (-1.031057 50.866878)
geometry
MULTIPOLYGON (((-1.031015 50.866874,-1.031017 50.866882,-1.031023 50.866890,-1.031032 50.866896,-1.031044 50.866900,-1.031057 50.866901,-1.031070 50.866900,-1.031082 50.866896,-1.031092 50.866890,-1.031098 50.866883,-1.031100 50.866874,-1.031098 50.866866,-1.031092 50.866858,-1.031083 50.866852,-1.031071 50.866848,-1.031058 50.866847,-1.031045 50.866848,-1.031033 50.866852,-1.031023 50.866858,-1.031017 50.866865,-1.031015 50.866874)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL